home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
QRZ! Ham Radio 4
/
QRZ Ham Radio Callsign Database - Volume 4.iso
/
digests
/
tcp
/
940102.txt
< prev
next >
Wrap
Internet Message Format
|
1994-11-13
|
4KB
Date: Sat, 28 May 94 04:30:05 PDT
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V94 #102
To: tcp-group-digest
TCP-Group Digest Sat, 28 May 94 Volume 94 : Issue 102
Today's Topics:
nos-bbs mail address hosed? (2 msgs)
unsubscribe aadamson@symantec.com
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Fri, 27 May 1994 11:24:35 -0500 (CDT)
From: Kurt Freiberger <kurt@cs.tamu.edu>
Subject: nos-bbs mail address hosed?
To: tcp-group@ucsd.edu (TCP-Group Mailing List)
Since nos-bbs and this'un are so closely interlinked... The
information for hydra.carleton.ca seems to be hosed. Can anyone else
post to nos-bbs? Even carleton.ca's nameservers don't have mx
records.
73/Kurt
--
# Kurt Freiberger, WB5BBW Dept. of Computer Science, TAMU #
# Internet: kurt@cs.tamu.edu | "Even MY hypocrisy has its limits." #
# AuralNet: 409/847-8607 | #
# AMPRNet: wb5bbw@wb5bbw.ampr.org | - "Doc" Holliday, Tombstone #
# Disclaimer: Not EVEN an official document of Texas A&M University #
------------------------------
Date: Fri, 27 May 94 23:54:00 -0000
From: mikebw@bilow.bilow.uu.ids.net (Mike Bilow)
Subject: nos-bbs mail address hosed?
To: tcp-group@UCSD.EDU
Cc: kurt@cs.tamu.edu
In a msg on <May 27 16:24>, Kurt Freiberger writes:
KF> Since nos-bbs and this'un are so closely interlinked... The
KF> information for hydra.carleton.ca seems to be hosed. Can anyone
KF> else post to nos-bbs? Even carleton.ca's nameservers don't
KF> have mx records.
There is no MX for hydra.carleton.ca, but there is an A record. If you mail
sender finds no MX, then it should go looking for the A record. It would
probably promote efficiency to have an MX record in order to prevent all of the
DNS queries that take place before getting the A record, but the mail should go
through fine in either case.
> carleton.ca.
Server: rs.internic.net
Address: 198.41.0.5
Non-authoritative answer:
carleton.ca nameserver = alfred.ccs.carleton.ca
carleton.ca nameserver = relay.cdnnet.ca
carleton.ca nameserver = james.ccs.carleton.ca
Authoritative answers can be found from:
carleton.ca nameserver = alfred.ccs.carleton.ca
carleton.ca nameserver = relay.cdnnet.ca
carleton.ca nameserver = james.ccs.carleton.ca
alfred.ccs.carleton.ca internet address = 134.117.1.1
relay.cdnnet.ca internet address = 192.73.5.1
james.ccs.carleton.ca internet address = 134.117.1.11
> lserver alfred.ccs.carleton.ca.
Default Server: alfred.ccs.carleton.ca
Address: 134.117.1.1
> set type=mx
> hydra.carleton.ca.
Server: alfred.ccs.carleton.ca
Address: 134.117.1.1
*** No mail exchanger (MX) records available for hydra.carleton.ca.
> set type=any
> hydra.carleton.ca.
Server: alfred.ccs.carleton.ca
Address: 134.117.1.1
hydra.carleton.ca internet address = 134.117.12.18
> set type=soa
> carleton.ca.
Server: alfred.ccs.carleton.ca
Address: 134.117.1.1
carleton.ca
origin = james.ccs.carleton.ca
mail addr = dns-admin.ccs.carleton.ca
serial = 13000834
refresh = 1800 (30 mins)
retry = 300 (5 mins)
expire = 3600000 (41 days 16 hours)
minimum ttl = 36000 (10 hours)
>
-- Mike
------------------------------
Date: Fri, 27 May 94 12:00:56 pst
From: "Alan Adamson" <aadamson@symantec.com>
Subject: unsubscribe aadamson@symantec.com
To: tcp-group@UCSD.EDU
unsubscribe aadamson@symantec.com
------------------------------
End of TCP-Group Digest V94 #102
******************************